E2E Test Scripts

Notes & Actions Module

Comprehensive end-to-end test coverage for CHAD2 Notes & Actions functionality across all user workflows and edge cases.

E2E-1: Create Single Note
Tests for creating notes on company and individual records, including date back-dating and validation rules.
Scope: Core Feature Feature: Note Creation Area: Notes Module
TC-1.1 Create Note on Company Record Hybrid
Notes Module / Create Note / Company Record
Difficulty: Low Est. Time: 5 min
  • User is logged in with Notes module access
  • Company record "ABC Corp" exists in the system
  • User has Creator role or equivalent permissions (ABC-1789)
Navigate to the Company record view for ABC Corp Expected: Company detail page loads with Notes panel visible on right sidebar
Click the New Note button in the Notes panel and verify the Create Note modal opens Expected: Modal displays with fields: Note Text, Category dropdown (ABC-1753), Type dropdown (ABC-1752), and Date picker defaulting to today
Enter note text "Follow up on Q2 budget review", select Category General, and Type Task Expected: All fields populate correctly. Date field shows current date
Click Save button to create the note (ABC-1786) Expected: Modal closes, note appears in Notes panel timeline, success toast notification displays "Note created successfully"
Verify the note displays the creator name, timestamp, category badge, and type indicator in the timeline Expected: Note renders with all metadata visible, Type label shows "Task" badge
Note creation modal fails to open or hangs when clicked on company with large number of existing notes
Category or Type dropdown values don't populate, showing blank or error states
Note text field doesn't trim whitespace, allowing leading/trailing spaces to be saved (data quality issue)
Success notification doesn't appear or note appears in timeline but backend save fails silently

This test validates the happy path for creating a basic note on a company record. Related JIRA: ABC-1784 (Company Notes), ABC-1786 (Notes Data). The Type field may become optional per ABC-1960.

JIRA: ABC-1784, ABC-1786, ABC-1960
TC-1.2 Create Note on Individual Record Hybrid
Notes Module / Create Note / Individual Record
Difficulty: Low Est. Time: 5 min
  • User is logged in with Notes module access
  • Individual contact "John Smith" exists in the system
  • User has Creator role with Individual Notes permission (ABC-1789)
Navigate to the Individual contact detail page for John Smith Expected: Contact detail page loads with Notes panel on the right sidebar
Click New Note button in the Notes panel Expected: Create Note modal opens with same fields as company notes (Text, Category, Type, Date)
Enter note text "Discussed Q3 objectives", Category Meeting Notes, Type Discussion Expected: Form fields populate without errors
Save the note and verify it appears in the Individual's Notes timeline (ABC-1783) Expected: Note created successfully, appears in timeline with proper metadata
Notes created on Individual incorrectly linked to Company or vice versa (wrong relationship binding)
Modal form validation rejects valid note text or category/type combinations specific to individuals
Timeline shows notes in wrong order or displays stale cached data from previous individual

Validates that individual notes are created and stored separately from company notes. Related JIRA: ABC-1783 (Individual Notes), ABC-1789 (Permissions).

JIRA: ABC-1783, ABC-1789
TC-1.3 Note Date Back-Dating & Validation Hybrid
Notes Module / Create Note / Date Validation
Difficulty: Medium Est. Time: 8 min
  • User is logged in with Notes module access
  • Company record exists in the system
  • System date/time is set correctly (not in DST transition)
Open company record and click New Note, verify Date field defaults to today Expected: Date picker shows current date pre-selected
Click the Date field and select a date 30 days in the past (back-dating enabled) Expected: Date picker allows selection of past dates, field updates to selected date
Try to select a date more than 90 days in the past (boundary test) Expected: System accepts the date or shows validation warning, depending on business rule (ABC-1786)
Attempt to select a future date (tomorrow or next week) Expected: System rejects future dates or prevents selection, shows validation error
Save a note with a back-dated date and verify the note appears in the timeline at the correct chronological position Expected: Note timeline re-sorts correctly, back-dated note appears in historical order, not at top
Date picker allows future dates when it should reject them, breaking timeline chronology
Back-dating beyond 90 days not validated, allowing incorrect historical records
Timeline doesn't re-sort after saving back-dated note, appears at top with wrong timestamp
Timezone conversion issues cause wrong date to be saved when user selects back-dated date

Tests date validation rules for note creation. Back-dating may be allowed for audit/history purposes, but future dates should be rejected. Related JIRA: ABC-1786 (Notes Data), ABC-1924 (Due Date rename suggests date handling changes).

JIRA: ABC-1786, ABC-1924
E2E-2: Create Single Action
Tests for creating actions on company and individual records with assignment and status workflow validation.
Scope: Core Feature Feature: Action Creation Area: Actions Module Critical Path
TC-2.1 Create Action on Company Record Hybrid
Actions Module / Create Action / Company Record
Difficulty: Low Est. Time: 6 min
  • User is logged in with Actions module access
  • Company record "ABC Corp" exists
  • User has Creator role for Actions (ABC-1789)
Navigate to Company record ABC Corp and locate the Actions panel Expected: Actions panel displays with New Action button visible
Click New Action and verify Create Action modal opens Expected: Modal displays with fields: Action Text, Category, Type (ABC-1960: optional), Due Date, Status (defaulting to Open), Assignee dropdown
Fill in: Action Text "Review annual contract", Category Legal, Due Date 5 days from now (ABC-1924) Expected: All fields populate correctly, due date shows 5 days in future
Leave Assignee blank (self-assign) and click Save (ABC-1785) Expected: Action created, modal closes, action appears in Actions panel with status Open and creator as assignee
Verify the action displays in the timeline with correct category badge, due date, and status indicator Expected: Action row shows text, category, due date with countdown, status badge, assignee avatar
Due date field rejects dates within valid range or shows wrong calculation of "days from now"
Type field not properly marked as optional, causing validation errors when left empty (ABC-1960)
Assignee defaults to creator but shows different user in the UI, causing confusion about who owns the action
Status defaults to something other than Open or doesn't appear in the workflow

Tests basic action creation on a company record. The Type field may become optional per ABC-1960. Due Date terminology may change per ABC-1924. Related JIRA: ABC-1784 (Company Actions), ABC-1785 (Actions Data), ABC-1789 (Permissions).

JIRA: ABC-1784, ABC-1785, ABC-1960, ABC-1924
TC-2.2 Create Action on Individual with Assignment Hybrid
Actions Module / Create Action / Individual with Assignment
Difficulty: Medium Est. Time: 7 min
  • User is logged in with Actions module access
  • Individual contact "Sarah Johnson" exists in the system
  • At least one other user exists in the system for assignment testing
Open Individual record Sarah Johnson and click New Action Expected: Create Action modal opens with all fields visible
Fill in Action Text "Send proposal", Category Sales, Due Date next Friday Expected: Form fields populate without errors
Click Assignee dropdown and select a different user Tom Richards (ABC-1789) Expected: Assignee dropdown populates with active users, selection applies without error
Save the action and verify it appears in the Individual's Actions panel with Tom assigned Expected: Action created, assignee avatar/name shows Tom Richards, status shows Open, creator and assignee are different
Verify Tom receives notification about the assigned action (if notification feature is enabled) Expected: Notification badge or email triggered for assigned user (ABC-1762, ABC-1763)
Assignee dropdown shows inactive or archived users, or doesn't show all available users
Assignment notification not sent or delivered to assigned user (breaks accountability)
Assignee field resets to creator when saving, ignoring the selected user
Permission boundary not enforced: assignee can't see or access the action (ABC-1789)

Tests assignment workflow and cross-user action creation. Validates that assigned users are notified and can access their assigned actions. Related JIRA: ABC-1783 (Individual Actions), ABC-1785 (Actions Data), ABC-1789 (Permissions), ABC-1762/1763 (Notifications).

JIRA: ABC-1783, ABC-1785, ABC-1789, ABC-1762, ABC-1763
TC-2.3 Action Due Date & Status Workflow Hybrid
Actions Module / Action Workflow / Due Date & Status
Difficulty: Medium Est. Time: 10 min
  • User is logged in with Actions module access
  • Company or Individual record exists
  • Action with due date in near future exists (created in TC-2.1 or TC-2.2)
Open the Actions panel and locate an action due in 5 days with status Open Expected: Action displays with due date countdown (e.g., "5 days"), status badge shows Open
Click the action row to open the action detail view and verify Status dropdown available Expected: Action detail/edit view opens with Status dropdown showing available options (e.g., Open, In Progress, Completed) (ABC-1924)
Change status to In Progress and save Expected: Status updates in the timeline, action may show different visual indicator (e.g., orange badge)
Change status to Completed and verify the due date countdown disappears Expected: Completed action shows green badge or strikethrough, countdown timer removed, action may move to completed section
Verify the completed action appears as a Note in the Notes panel (ABC-1768) Expected: Completed action converted to note in Notes timeline, preserves original text and date, shows completion metadata
Status dropdown doesn't update or changes don't persist, reverting to previous status
Due date countdown continues to display even after action is completed, causing confusion about actual deadlines
Completed action not converted to note, or conversion occurs but loses original data (ABC-1768)
Status workflow allows invalid transitions (e.g., Completed back to Open), breaking business logic

Tests the complete action lifecycle from creation to completion. Validates due date handling (ABC-1924) and conversion of completed actions to notes (ABC-1768). Related JIRA: ABC-1785 (Actions Data), ABC-1924 (Due Date rename), ABC-1768 (Convert Completed Action).

JIRA: ABC-1785, ABC-1924, ABC-1768
E2E-3: Global Notes & Actions
Tests for creating global notes and actions from Selective Reporting with proper prefix text validation.
Scope: Integration Feature Feature: Global Notes/Actions Area: Selective Reporting Integration
TC-3.1 Create Global Note from Selective Reporting Hybrid
Global Notes & Actions / Selective Reporting Integration / Global Note
Difficulty: Medium Est. Time: 8 min
  • User is logged in with Global Notes access
  • Selective Reporting module available and configured
  • At least two companies (e.g., "ABC Corp", "XYZ Inc") exist in the system
Open Selective Reporting and select multiple companies: ABC Corp and XYZ Inc (ABC-1779) Expected: Selective Reporting view displays both companies selected
Locate the Create Global Note action in the reporting interface and click it Expected: Global Note creation modal opens with a text field and relevant metadata fields
Enter note text "Q3 pricing review" and save Expected: Global note created successfully and applied to both selected companies
Verify the note appears in ABC Corp's Notes panel with proper prefix text (e.g., "[Global]") (ABC-1779) Expected: Note displays with global indicator/badge, timestamp, and creator information
Verify the same note also appears in XYZ Inc's Notes panel with identical text and metadata Expected: Note appears in both company records, proving global note linking works correctly
Global Note creation modal doesn't appear or is hidden in Selective Reporting interface
Global note created but only applies to one company instead of all selected (partial application)
Global note prefix text missing or inconsistent across the selected companies
Global note text truncated or corrupted when saved to multiple records

Tests the integration between Selective Reporting and the Notes module for creating notes across multiple companies simultaneously. The global note should have a distinguishing prefix (e.g., "[Global]") to indicate its scope. Related JIRA: ABC-1779 (Global Companies), ABC-1753 (Categories).

JIRA: ABC-1779, ABC-1753
TC-3.2 Create Global Action from Selective Reporting Hybrid
Global Notes & Actions / Selective Reporting Integration / Global Action
Difficulty: Medium Est. Time: 10 min
  • User is logged in with Global Actions access
  • Selective Reporting module available and configured
  • At least two companies selected in Selective Reporting
Open Selective Reporting with multiple companies selected and click Create Global Action Expected: Global Action creation modal opens with Action Text, Category, Type, Due Date, and Assignee fields
Fill in: Action Text "Annual compliance audit", Category Compliance, Due Date 30 days out, Assignee Sarah Johnson Expected: All fields populate without validation errors
Save the global action and verify it creates on all selected companies Expected: Action successfully created, returns to Selective Reporting view
Navigate to each selected company and verify the global action appears with the same text and assignee Expected: Action visible in Actions panel of both companies, assigned to Sarah Johnson, due date matches
Global action creation modal not accessible from Selective Reporting or shows disabled state
Global action created but assignee not properly linked across multiple companies, showing different assignee per company
Partial creation: action applies to some companies but not others
Due date not preserved correctly when action synced to multiple companies

Tests global action creation across multiple companies. Validates that the assignment and due date are consistent across all linked records. Related JIRA: ABC-1779 (Global Companies), ABC-1785 (Actions Data), ABC-1752 (Types).

JIRA: ABC-1779, ABC-1785, ABC-1752
TC-3.3 Global Note/Action Prefix Text Verification Manual
Global Notes & Actions / Prefix Text Validation
Difficulty: Low Est. Time: 6 min
  • Global notes and actions from TC-3.1 and TC-3.2 are created and visible
  • User is logged in and can view Notes and Actions panels
Open company record and examine the global note created in TC-3.1 Expected: Note displays with a clear prefix indicator (e.g., "[Global]", "[Multi-Company]", or distinct visual badge)
Verify the prefix text is consistent across all companies that received the global note Expected: Same prefix appears in all linked company records (no variations or formatting differences)
Examine the global action from TC-3.2 and verify it has the same prefix indicator as the global note Expected: Both global notes and actions use consistent prefix formatting for easy identification
Compare a regular (non-global) note/action with a global one and verify they are visually distinguishable Expected: Global items have distinctive badge, color, or prefix that clearly separates them from regular notes/actions
Prefix text missing entirely, making global notes/actions indistinguishable from regular ones
Prefix text inconsistent across companies (e.g., "[Global]" in one company, "[Multi]" in another)
Prefix text appears in wrong location (beginning/end of note text instead of dedicated field or badge)
Visual distinction between global and regular items unclear or confusing to users

Manual validation of prefix text consistency for global notes and actions. Ensures users can quickly identify which items are global (multi-company) vs. specific to a single record. Related JIRA: ABC-1779 (Global Companies), ABC-1778 (Global Individuals).

JIRA: ABC-1779, ABC-1778
E2E-4: Action Checklists
Tests for attaching action checklists to companies and individuals, including date offset verification.
Scope: Advanced Feature Feature: Action Checklists Area: Workflow Automation
TC-4.1 Attach Action Checklist to Company Hybrid
Action Checklists / Attach to Company
Difficulty: Medium Est. Time: 8 min
  • User is logged in with Actions module access
  • Company record "ABC Corp" exists
  • Action Checklist template exists (e.g., "Onboarding Checklist") with multiple checklist items (ABC-1751)
Open company record ABC Corp and locate the Actions panel Expected: Actions panel displays with New Action and additional menu options visible
Click menu (or find button for) Attach Checklist and verify available templates load Expected: Checklist selection modal opens showing available templates (e.g., "Onboarding Checklist", "Sales Checklist")
Select the Onboarding Checklist template (ABC-1751) Expected: Template selected, checklist items preview displays (e.g., "Create account", "Set up permissions", "Schedule kickoff")
Confirm the attachment and verify multiple actions are created in the Actions panel Expected: Each checklist item becomes an individual action with status Open and default due date
Verify each action displays the checklist item text, category, and is marked as part of the checklist (ABC-1773) Expected: Actions show "Onboarding Checklist" indicator, sequential numbering or grouping visible in panel
Attach Checklist button not visible or disabled, preventing checklist functionality
Checklist template selection modal doesn't load or templates list is empty
Only partial checklist items attached (e.g., first 2 of 5 items), others missing
Created actions from checklist don't show checklist grouping indicator, appearing as disconnected individual actions

Tests the attachment of predefined action checklists to company records. This feature allows batch creation of related actions for common workflows (e.g., onboarding). Related JIRA: ABC-1773 (Checklist to Company), ABC-1751 (Checklists), ABC-1785 (Actions Data).

JIRA: ABC-1773, ABC-1751, ABC-1785
TC-4.2 Attach Action Checklist to Individual Hybrid
Action Checklists / Attach to Individual
Difficulty: Medium Est. Time: 8 min
  • User is logged in with Actions module access
  • Individual contact "Sarah Johnson" exists
  • Action Checklist templates available (ABC-1751)
Open Individual record Sarah Johnson and locate the Actions panel Expected: Actions panel displays with New Action and menu/attachment options visible
Click Attach Checklist and select a template (e.g., Onboarding Checklist) Expected: Checklist modal opens, template selection works, preview of items displays
Confirm the attachment and verify all checklist items become individual actions (ABC-1772) Expected: Multiple actions created in Individual's Actions panel, all tied to the same checklist
Verify the checklist indicator appears for each action and distinguishes them from standalone actions Expected: Actions show checklist grouping, perhaps with a checkbox or hierarchical indicator
Attach Checklist option not available for individual records (feature inconsistently implemented)
Checklist items not properly linked to the individual, appearing under company instead
Attachment succeeds but actions don't appear in the timeline or are hidden
Checklist grouping metadata lost, actions appear disconnected or with different categories

Tests that action checklists can be attached to individual records just as they are to companies. Validates feature consistency across entity types. Related JIRA: ABC-1772 (Checklist to Individual), ABC-1751 (Checklists).

JIRA: ABC-1772, ABC-1751
TC-4.3 Action Checklist Date Offset Verification Manual
Action Checklists / Date Offset Validation
Difficulty: Medium Est. Time: 8 min
  • Action Checklists from TC-4.1 or TC-4.2 are created and visible
  • Checklist template has date offset configuration (e.g., items have +3 days, +5 days, +10 days relative offsets)
  • Admin has configured checklist date offsets per ABC-1751
Examine the due dates of the checklist actions created in TC-4.1 Expected: Multiple actions visible with different due dates (e.g., Item 1 due in 3 days, Item 2 due in 5 days, Item 3 due in 10 days)
Verify the date offsets match the checklist template configuration (e.g., if template says "+5 days", first action should be 5 days from today) Expected: Calculated due dates are correct and match template settings
Verify the sequential order of the checklist items (e.g., Step 1 due soonest, Step 5 due latest) Expected: Actions display in ascending order by due date, creating a logical workflow progression
Check for any timezone or DST-related date calculation issues by comparing with calendar Expected: Due dates are accurate and account for timezone/DST correctly
Date offsets not applied, all checklist actions have same due date (today or random date)
Offset calculations incorrect (e.g., "+5 days" calculates as +3 days or +7 days)
Timezone conversion causes due dates to be off by a day or more
Sequential order of actions doesn't match due date order, creating confusing workflow

Tests that action checklists apply correct date offsets based on template configuration. This ensures that multi-step workflows have proper sequencing with staggered due dates to prevent bottlenecks. Related JIRA: ABC-1751 (Checklists), ABC-1924 (Due Date rename).

JIRA: ABC-1751, ABC-1924
E2E-5: Browse & Filter Notes/Actions
Tests for browsing, filtering, and viewing notes and actions with various criteria and permission boundaries.
Scope: Core Feature Feature: Browse & Filter Area: Notes & Actions Module
TC-5.1 Browse Default View - Actions Assigned to Me Hybrid
Browse & Filter / Default View
Difficulty: Low Est. Time: 5 min
  • User logged in with Level 1 Contacts permission
  • Multiple notes and actions exist across companies/individuals
  • Actions assigned to current user and other users exist
Navigate to main nav Notes & Actions Expected: Browse screen loads with list of notes and actions
Verify default filter is "Actions Assigned to Me" (ABC-1759) Expected: Only current user's assigned actions display, no notes appear
Verify sort order: Type ascending then Date descending Expected: Actions grouped by Type (Action first), within each group sorted by Date newest first
Verify all column headers present: Type, Related To Type, Related To Name, Created By, Assigned To, Date, Due Date, Status, Last Modified Date, Text Expected: All 10 columns visible with appropriate data, columns properly aligned
Default filter not applied on first load, showing all notes/actions
Actions assigned to other users appearing in default view
Sort order incorrect (e.g., Date ascending instead of descending)
Missing columns in table header

Validates default filtering and display behavior when accessing Browse Notes & Actions. This ensures users immediately see their relevant work items. Related JIRA: ABC-1759 (Browse Filter), ABC-2005 (Default View).

JIRA: ABC-1759, ABC-2005
TC-5.2 Filter by Type, Related To, and Date Range Hybrid
Browse & Filter / Filter Criteria
Difficulty: Medium Est. Time: 8 min
  • User on Browse Notes & Actions screen
  • Mix of notes and actions for companies and individuals exists
  • Actions with various due dates exist
Use Type filter "Note" — verify only notes display Expected: All actions hidden, only notes visible in list
Switch to Type "Action" — verify only actions display Expected: All notes hidden, only actions visible
Filter by Related To Type "Company" — verify only company-related items show Expected: All individual-related items hidden, only company items visible
Use Related To search for specific company name (e.g., ABC Corp) Expected: List filtered to show only items related to ABC Corp, partial name matches included
Filter by Due Date range (e.g., next 7 days) Expected: Only items with due dates in range display
Clear all filters — verify all items return (ABC-1759) Expected: All notes and actions display again, no filters active
Filters not combining correctly when multiple criteria applied
String search not matching partial names (case sensitivity issue)
Date range boundaries incorrect (off-by-one errors)
Clear filters not resetting all criteria at once

Tests filtering capabilities to ensure users can narrow results using multiple criteria. Validates AND logic between filter types and string matching behavior. Related JIRA: ABC-1759 (Browse Filter).

JIRA: ABC-1759
TC-5.3 View Modal Read-Only Verification Manual
Browse & Filter / View Modal
Difficulty: Low Est. Time: 5 min
  • User on Browse Notes & Actions screen
  • Notes and actions with various data visible
Click a note row to open view modal Expected: Modal opens in read-only state
Verify all fields are displayed read-only (no input fields, no edit buttons, no save button) Expected: All form fields appear as static text only
Attempt keyboard shortcuts (Ctrl+E, etc.) — verify no edit mode activated Expected: Shortcuts ignored, modal remains in view mode
Close modal with X button Expected: Modal closes, user returns to browse list
Open an action record and verify Assigned To, Due Date, Status all read-only Expected: All action fields display as static text, no edit capability
Verify no "Edit" button in modal (ABC-1927) Expected: Edit button absent from view modal
Edit controls appearing in view modal
Double-click enabling edit mode
Form fields appearing editable instead of static
Save/Cancel buttons visible in modal

Validates that view-only modals enforce read-only state across all fields and prevent accidental editing. Critical for data integrity in shared views. Related JIRA: ABC-1927 (View Modal).

JIRA: ABC-1927
E2E-6: Dashboard & Notifications
Tests for dashboard widgets, notification badges, and action completion workflows.
Scope: Core Feature Feature: Dashboard Integration Area: Notifications & UI
TC-6.1 Dashboard Widget - Incomplete Actions Display Hybrid
Dashboard & Notifications / Widget Display
Difficulty: Medium Est. Time: 6 min
  • User logged in
  • Multiple incomplete actions assigned to current user
  • Actions with varying ages exist
Navigate to main dashboard Expected: Dashboard loads with widget panels visible
Locate "My Next Actions" widget Expected: Widget present on dashboard showing action list
Verify all incomplete assigned actions shown (ABC-1757) Expected: All open actions for current user display in widget
Verify data columns present: Date Assigned, Assigned-by, Related-To Entity Expected: All three columns visible with correct data populated
Verify sort order: oldest actions first Expected: Actions sorted by date assigned, oldest at top
Verify ability to click "Edit" to go to action edit screen Expected: Edit link present and navigates to action edit page
Widget not loading or showing blank state
Missing older actions in widget display
Sort order showing newest first instead of oldest
Edit link not navigating correctly to action edit screen

Validates that the dashboard widget properly displays and sorts incomplete actions. This widget serves as a quick-access hub for pending work items. Related JIRA: ABC-1757 (Dashboard Widget).

JIRA: ABC-1757
TC-6.2 Notification Badge Count & Bell Icon Hybrid
Dashboard & Notifications / Notification Badge
Difficulty: Low Est. Time: 5 min
  • User logged in
  • Known number of incomplete actions assigned to current user (e.g., 5)
Check Notes & Actions main nav item — verify badge shows correct count (ABC-1762) Expected: Badge displays "5" matching the incomplete action count
Click bell icon in upper-right corner Expected: Notification dropdown opens
Verify dropdown displays: "You currently have 5 actions assigned to you. Click here to view a list of actions assigned to you." (ABC-1763) Expected: Notification text matches actual count, message clear and actionable
Click the notification message Expected: Navigate to Browse Notes & Actions screen
Verify default view shows current user's actions Expected: Browse screen displays "Actions Assigned to Me" filter active
Badge count incorrect or not updating
Bell icon missing dropdown or dropdown not opening
Notification text not matching actual count
Navigation not working from notification click

Validates notification system integration with badge counting and bell icon dropdown. Tests both visual indicators (badge) and interactive elements (bell dropdown). Related JIRA: ABC-1762 (Badge), ABC-1763 (Bell Icon).

JIRA: ABC-1762, ABC-1763
TC-6.3 Complete Action from Dashboard Widget Hybrid
Dashboard & Notifications / Complete Action
Difficulty: Medium Est. Time: 7 min
  • User on main dashboard
  • At least one incomplete action visible in widget
  • Badge count noted (e.g., 5)
Click "Complete" button on an action in dashboard widget Expected: Action marked as complete
Verify confirmation dialog appears (if applicable) Expected: User prompted to confirm completion
Verify action disappears from widget (ABC-1757) Expected: Completed action removed from "My Next Actions" list
Verify badge count decrements to 4 Expected: Badge updates immediately from 5 to 4
Navigate to Browse All and find the completed action Expected: Browse screen loads, action findable via filters
Verify completed action now shows Type="Note" with Status="Complete" (ABC-1768) Expected: Type converted to Note, Status shows "Complete"
Verify Assigned To and Due Date persist Expected: Original assignment and due date still visible
Complete button not updating status in backend
Action still showing in widget after completion
Badge count not decrementing
Type not converting to Note, or original data not persisting

Tests the complete action workflow from dashboard widget, including UI updates and data transformation. Ensures badge count and widget state stay synchronized with backend status changes. Related JIRA: ABC-1757 (Dashboard Widget), ABC-1768 (Completion).

JIRA: ABC-1757, ABC-1768
E2E-7: Admin - Categories, Types & Checklists
Tests for admin configuration of categories, types, and action checklists in the system.
Scope: Admin Feature Feature: Admin Settings Area: System Configuration Critical: Admin-only
TC-7.1 Manage Note/Action Categories Hybrid
Admin Settings / Manage Categories
Difficulty: Low Est. Time: 6 min
  • Admin user logged in
  • Existing categories visible in admin
Navigate to Admin > Manage Categories Expected: Categories admin page loads showing list of existing categories
Click "Add Category" Expected: New category form opens or appears
Enter name "QA Test Category" and save Expected: Category appears in list as Enabled
Toggle category status to Disabled Expected: Status changes to Disabled in admin list
Navigate to create a new note (ABC-1753) Expected: Create note form opens
Verify "QA Test Category" does NOT appear in category dropdown Expected: Disabled category hidden from user selection
Re-enable the category in admin Expected: Status changes back to Enabled
Return to create note form and verify it appears again Expected: "QA Test Category" now visible in category dropdown
New category not saving properly
Disabled category still showing in user-facing dropdowns
Toggle not persisting state across page refreshes
Category appearing for wrong module

Validates category management including create, enable/disable, and visibility in user forms. Tests the relationship between admin configuration and end-user UI. Related JIRA: ABC-1753 (Categories).

JIRA: ABC-1753
TC-7.2 Manage Note/Action Types with Prefix Hybrid
Admin Settings / Manage Types
Difficulty: Medium Est. Time: 7 min
  • Admin user logged in
  • Existing types visible in admin
Navigate to Admin > Manage Types Expected: Types admin page loads with existing types listed
Click "Add Type" Expected: New type form opens with fields visible
Enter Name "Follow-Up Call", Description "Post-meeting follow-up", Prefix "FU:" Expected: All fields accept input without errors
Save the type and verify in list (ABC-1752) Expected: New type appears in types list as Enabled
Create a new note with the "Follow-Up Call" type Expected: Note creation form opens, new type selectable
Verify note text starts with prefix "FU:" Expected: Prefix automatically prepended to note text on creation
Toggle type to Disabled in admin Expected: Status changes to Disabled
Verify it doesn't appear when creating new notes Expected: Disabled type hidden from user dropdown
Prefix not prepending to note text on creation
Disabled type still selectable in dropdowns
Description not saving or displaying
Type name duplicates allowed without validation

Validates type management with prefix functionality. Ensures prefixes auto-apply on note creation and that admin enable/disable controls properly gate user access. Related JIRA: ABC-1752 (Types).

JIRA: ABC-1752
TC-7.3 Create & Copy Action Checklists Hybrid
Admin Settings / Action Checklists
Difficulty: High Est. Time: 10 min
  • Admin user logged in
  • At least one existing checklist in admin
Navigate to Admin > Action Checklists Expected: Checklists admin page loads with existing templates listed
Click "Create Checklist" Expected: New checklist form opens
Enter Name "New Member Onboarding", Description "Checklist for new member companies", Module "Companies" Expected: Header fields populate correctly
Add Action 1: "Send welcome packet" offset +7 days Expected: Action item added to checklist
Add Action 2: "Schedule intro call" offset +14 days Expected: Second action item added to checklist
Add Action 3: "Verify dues setup" offset +30 days Expected: Third action item added with correct offset
Save the checklist (ABC-1751) Expected: Checklist created and appears in list
Click "Copy" on the new checklist Expected: Copy functionality initiated
Verify copy has same 3 actions with same offsets Expected: All actions and date offsets duplicated correctly
Edit copy — rename to "Returning Member Onboarding" and save Expected: Copied checklist renamed and persisted
Date offsets not calculating correctly (e.g., +7 shows as +5 or +9)
Copy not duplicating all actions, missing some items
Module assignment not persisting across save/edit
Checklist name not validated for uniqueness

Tests complete checklist lifecycle: create with multiple actions and date offsets, copy with full action duplication, and edit. Validates date offset math and module context preservation. Related JIRA: ABC-1751 (Checklists).

JIRA: ABC-1751
E2E-8: Permissions & Edge Cases
Tests for permission boundaries, action completion workflows, and reporting edge cases.
Scope: Security & Data Feature: Permissions & Reporting Area: Access Control Critical: Security
TC-8.1 Permission Boundary - Creator vs Assignee vs Other Manual
Permissions & Edge Cases / Permission Boundaries
Difficulty: High Est. Time: 15 min
  • Three different user accounts (User A, User B, User C) all with Level 1 Contacts permission
  • Company record available
As User A — create an action on a company, assign to User B Expected: Action created and assigned successfully
As User A (creator): verify Edit and Delete buttons visible Expected: Both Edit and Delete action buttons appear
Edit the action text (ABC-1789) Expected: Edit succeeds, changes persist
As User B (assignee): open same action Expected: Action visible to assignee
Verify Edit button visible but Delete button NOT visible Expected: Only Edit available to assignee, no Delete
Edit action text as User B Expected: Edit succeeds for assignee
As User C (neither creator nor assignee): open same action Expected: Action visible with read-only view
Verify NO Edit or Delete buttons visible Expected: No edit controls for non-creator, non-assignee
Create a note as User A Expected: Note created successfully
As User B: verify cannot edit or delete note Expected: No edit/delete buttons for non-creator (only creator can modify notes)
Assignee able to delete actions (should be creator-only)
Non-creator/assignee able to edit records
Permission checks only on UI, API bypass possible
Deleted action still visible to other users (orphaned reference)

Tests permission model: creator has full control (edit/delete), assignee can edit actions only, others have read-only. Validates both UI controls and backend enforcement. Must test across three users to fully verify boundaries. Related JIRA: ABC-1789 (Permissions), ABC-1937 (Notes Edit).

JIRA: ABC-1789, ABC-1937
TC-8.2 Completed Action Displays as Note Hybrid
Permissions & Edge Cases / Action Completion
Difficulty: Medium Est. Time: 6 min
  • An open action exists with Due Date, Assigned To, and other fields populated
Open the action record Expected: Action detail view displays with all fields visible
Change Status to "Complete" Expected: Status field updates
Save/confirm the status change Expected: Changes persisted to backend
Navigate to Browse All Notes & Actions Expected: Browse screen loads
Find the completed action in the list Expected: Completed action appears in browse results
Verify Type column shows "Note" (ABC-1768) Expected: Type converted from Action to Note
Verify Status shows "Complete" Expected: Status field displays as Complete
Verify Assigned To and Due Date persist (not cleared) Expected: Original assignment and due date still visible
Sort by Type — verify completed actions sort with other Notes Expected: Completed action groups with Note type items
Type not converting to Note on completion
Assigned To or Due Date cleared when status changes
Status not persisting after save
Sort grouping incorrect, completed actions not grouping with Notes

Tests the data transformation that occurs when an action is marked complete: type changes from Action to Note, but all original metadata persists. Validates sort behavior after type change. Related JIRA: ABC-1768 (Completion).

JIRA: ABC-1768
TC-8.3 Selective Reporting Export with Notes/Actions Hybrid
Permissions & Edge Cases / Reporting Export
Difficulty: High Est. Time: 10 min
  • Companies with notes/actions exist
  • User has Contacts Level 1 permission
Navigate to Contacts Selective Reporting Expected: Reporting interface loads
Select criteria to include companies with notes Expected: Filter criteria accepts notes selection
Check "Include Notes/Actions" in output options (ABC-1755, ABC-1754) Expected: Output options include Notes/Actions checkbox
Run report Expected: Report generation completes
Export to Excel format Expected: Excel file downloads
Open Excel — verify notes/actions columns present with correct data Expected: Notes/actions content appears in spreadsheet with all metadata
Export to PDF format Expected: PDF file downloads
Open PDF — verify notes/actions included in output Expected: PDF displays notes/actions data with proper formatting
Notes/Actions option not appearing in output settings
Excel missing note text column or showing blank values
PDF formatting broken with long notes (text overflow)
Export not including all notes for selected companies

Tests selective reporting with notes/actions data export in Excel and PDF formats. Validates that notes/actions are properly included in multi-format exports and that formatting handles variable-length note text. Related JIRA: ABC-1755 (Excel Export), ABC-1754 (PDF Export).

JIRA: ABC-1755, ABC-1754

CHAD2 Notes & Actions - E2E Test Scripts | Last Updated: 2026-04-07 | 8 Flows, 24 Test Cases